Objective

Refactor the engine to consume core data structures and utility algorithms from the external vifaa package instead of maintaining duplicated internal implementations.

Solution

The engine previously maintained its own implementations of foundational data structures and utility algorithms such as:

• DenseList
• Graph / GraphList
• IndexAllocator
• Bitset
• Pool
• ArrayView
• Range
• Number packing utilities

These implementations duplicated functionality that now exists in vifaa. This migrates the engine to vifaa@0.3.0, removes the internal copies, and updates dependent systems to use the external package.

Why this approach:

• Eliminates duplicate maintenance across projects.
• Centralizes fixes and optimizations in a single shared package.
• Reduces engine code size and maintenance burden.
• Ensures all projects consume the same tested implementations.
• Allows datastructure improvements to ship independently of engine releases.

Showcase

N/A

Migration guide

No migration required

Notes

• Datastructure bugs and optimizations should now be addressed in vifaa.
• The engine no longer exports the algorithms module.
• Existing consumers should migrate to the vifaa equivalents where applicable.
• Asset and ECS systems have already been updated internally.

Checklist

• I have updated the documentation accordingly.
• I have added tests to cover my changes.

The test checkbox is left unchecked because this PR removes the engine-owned datastructure tests and relies on the external vifaa package's test suite rather than adding new tests within this repository.